-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: allow extensions to attach chat context #213172
Conversation
* @param value - The value of the chat context. | ||
* @param location - The location of the chat context. | ||
*/ | ||
export function attachContext(name: string, value: string | Uri | Location | unknown, location: ChatLocation.Panel): void; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should have an ID actually
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should VS Code actually be doing this for stuff likes files and selections? #file
and the new attachment picker are still totally driven from core right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah they're still totally driven by core, I'd like to also have #file
extension land though because it's effectively a dynamic variable resolver but is special cased in a bunch of places right now.
* feat: allow extensions to attach chat context * fix: allow attaching different ranges from same file * fix: restore accepting files from picker
No description provided.